Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: chrono Date range 0.. to 1.. #191

Merged
merged 1 commit into from
Aug 28, 2024
Merged

fix: chrono Date range 0.. to 1.. #191

merged 1 commit into from
Aug 28, 2024

Conversation

foolishell
Copy link
Contributor

Background

The year 0000 does not exist by definition, which occasionally causes errors in programs.

By ChatGPT

The year "0000" is generally considered invalid.

  1. Gregorian and Julian Calendars : These calendars start from year 1. There is no year 0; thus, "0000" is invalid.
  2. ISO 8601 : This international standard allows "0000" to represent the year before 1 AD (i.e., 1 BC). However, this usage is specialized and not common in everyday contexts.
  3. Programming and Databases : Some systems and databases may permit "0000", but this is due to specific technical requirements and is not standard practice.
  4. Historical and Archaeological Contexts : In these fields, the convention is that there is no year 0. The year before 1 AD is 1 BC.
    Overall, in most standard and everyday contexts, "0000" is not a valid year.

@cksac cksac merged commit adee7cf into cksac:master Aug 28, 2024
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants